This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
I don't know the solution to your problem, but I've spent my fair share of time working with the domain indexer task (I use it to index large file systems). Here are some useful console commands:
tell domidx q - Stops indexer
load domidx -d - Deletes the index
load domidx -s - Starts the indexer without a delay
I'd stop the indexer, delete the index, and start it up again. Watch the console for a little while....does the domidx task start listing the databases it is indexing? In domino administrator, does the domain index task use a lot of CPU? If the databases are large, it might take quite a while for the first indexing run to complete....you'll see high CPU usage (50%-75%) for the domain indexer until it finishes.
Feedback response number WEBB83UP4V created by ~Fred Deslubergynds on 03/24/2010